Configuring middleware in the component #3937

hhunter-ms · 2024-01-04T15:40:36Z

Description

New doc for configuring middleware
Add new middleware node under 'Developing Applications/Components"

Issue reference

PR will close: #3917

Signed-off-by: Hannah Hunter <[email protected]>

…issue_3917

daprdocs/content/en/operations/components/middleware.md

daprdocs/content/en/reference/components-reference/supported-middleware/middleware-oauth2.md

...en/reference/components-reference/supported-middleware/middleware-oauth2clientcredentials.md

daprdocs/content/en/reference/components-reference/supported-middleware/middleware-opa.md

...docs/content/en/reference/components-reference/supported-middleware/middleware-rate-limit.md

daprdocs/content/en/reference/components-reference/supported-middleware/middleware-uppercase.md

daprdocs/content/en/reference/components-reference/supported-middleware/middleware-wasm.md

daprdocs/content/en/operations/components/middleware.md

sadath-12 · 2024-01-09T19:40:54Z

Thanks for the pr @hhunter-ms . left some comments

daprdocs/content/en/operations/components/middleware.md

sadath-12 · 2024-01-09T19:45:12Z

consider also adding these points --

We are adding 2 new metadata options (all keys and values are handled as case-insensitive):
pipeline can be set to httpPipeline or appHttpPipeline (we'll have aliases including http-pipeline and http for the first; app-http-pipeline and app for the second)
priority is an integer from -MaxInt32 to +MaxInt32
Both metadata options are required for the component to be enabled in a pipeline. For backwards-compatibility, there's no default priority.

Components with lower priorities are executed first
Priorities don't necessarily need to be sequential. In the docs, we will document as best practice the use of values like "100", "200", "300", etc - so changing the order is less complex

just pasting it from the design issue. you can re-fashion it

Signed-off-by: Hannah Hunter <[email protected]>

msfussell

I would make sure you read the proposal conclusion for this feature here dapr/dapr#6660 (comment) for each of my comments

daprdocs/content/en/developing-applications/develop-components/middleware-components/_index.md

...nt/en/developing-applications/develop-components/middleware-components/develop-middleware.md

daprdocs/content/en/reference/components-reference/supported-middleware/middleware-bearer.md

daprdocs/content/en/reference/components-reference/supported-middleware/middleware-oauth2.md

...en/reference/components-reference/supported-middleware/middleware-oauth2clientcredentials.md

Signed-off-by: Hannah Hunter <[email protected]>

msfussell · 2025-08-29T04:02:30Z

Closing PR, as code issue closed

set up docs for configuring middleware components

d337f08

Signed-off-by: Hannah Hunter <[email protected]>

hhunter-ms added this to the 1.13 milestone Jan 4, 2024

hhunter-ms self-assigned this Jan 4, 2024

initial edits

7130359

Signed-off-by: Hannah Hunter <[email protected]>

hhunter-ms requested a review from sadath-12 January 5, 2024 14:47

hhunter-ms and others added 5 commits January 5, 2024 12:49

remove new doc; unnecessary

f72007e

Signed-off-by: Hannah Hunter <[email protected]>

updates

338d268

Signed-off-by: Hannah Hunter <[email protected]>

Merge branch 'v1.13' into issue_3917

9aff7f8

add to specs

9440d21

Signed-off-by: Hannah Hunter <[email protected]>

Merge branch 'issue_3917' of https://github.com/hhunter-ms/docs into …

b0fa100

…issue_3917

msfussell added the do-not-merge label Jan 9, 2024

hhunter-ms marked this pull request as ready for review January 9, 2024 17:25

hhunter-ms requested review from a team as code owners January 9, 2024 17:25